Detc 2012 - 70272 Dependency Modeling and Model Management in Mechatronic Design

Mechatronic design is traditionally supported through domain-specific design activities throughout the product development process. The partitioning into domain-specific problems leads to a situation where product properties influence each other, hence giving rise to dependencies. These dependencies play a key role in prediction of properties and as a result, in the decision making process. The important question is: how to manage the dependencies for an efficient and effective decision making? The aim of this paper is threefold. Firstly, we investigate the nature of dependencies and study how to model them. The paper proposes appropriate language constructs taking into account synthesis and analysis nature of properties and dependencies. The concepts related to the dependency modeling are then illustrated through a simple robot design example, where the creation and importance of a dependency model are explained. Secondly, we study practical approaches for consistency management and model management in the presence of dependencies. Six levels-ofdetail in modeling dependencies are presented; emphasizing that modeling at higher level-of-detail ensures that more inconsistencies are avoided. Available languages such as OMG SysMLTM are evaluated for a possible creation of the dependency models leading towards executable dependency networks. However, at present, SysML does not provide sufficiently rich language constructs to model dependencies. Thirdly, we compare our dependency modeling approach to the other state-of-the-art approaches such as dependency modeling with a Design Structure Matrix, and highlight the benefits of the language constructs proposed in this paper. We aim to convince the reader that there is a substantial value in modeling dependencies explicitly, especially to avoid inconsistencies, which is not the current state of the practice. However, an overall value from dependency modeling can only be obtained if the cost of creating the dependency model is reasonable. Issues such as human interaction/effort and model management through PLM are discussed.